Skip to content

docs: add cache-control best practices to static deployment guide#21706

Open
amariecarysta wants to merge 1 commit intovitejs:mainfrom
amariecarysta:main
Open

docs: add cache-control best practices to static deployment guide#21706
amariecarysta wants to merge 1 commit intovitejs:mainfrom
amariecarysta:main

Conversation

@amariecarysta
Copy link

Fixes #20064

Adds documentation to the Static Deployment guide explaining recommended cache-control headers for Vite build assets.

Since Vite generates hashed filenames for assets, they can be safely cached long-term.

This change is documentation-only. No code behavior is changed.

@bluwy
Copy link
Member

bluwy commented Feb 26, 2026

Can we add this info to each of the deployment sections so users know what to do for the specific hosting platform? As a start, I think documenting for GitHub, Netlify, Vercel, and Cloudflare should be enough.

@sapphi-red sapphi-red added the documentation Improvements or additions to documentation label Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document cache-control best practice

3 participants